-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wiring context for EVM Keys API #11800
Conversation
I see that you haven't updated any CHANGELOG files. Would it make sense to do so? |
1d8e874
to
9eeb413
Compare
125f45c
to
4cd18c3
Compare
e6bbbe8
to
8448f0c
Compare
bf5f3f5
to
b66cb73
Compare
b66cb73
to
61f8f6c
Compare
d61f6c1
to
8713b34
Compare
9acf905
to
b79255f
Compare
@@ -177,7 +177,7 @@ func newFunctionsContractTransmitter(contractVersion uint32, rargs commontypes.R | |||
if sendingKeysLength > 1 && s == effectiveTransmitterAddress.String() { | |||
return nil, errors.New("the transmitter is a local sending key with transaction forwarding enabled") | |||
} | |||
if err := ethKeystore.CheckEnabled(common.HexToAddress(s), configWatcher.chain.Config().EVM().ChainID()); err != nil { | |||
if err := ethKeystore.CheckEnabled(ctx, common.HexToAddress(s), configWatcher.chain.Config().EVM().ChainID()); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should create a ticket to follow up with investigating each constructor that now requires context. Hopefully they are all just database related, but even that can be a problem, since a temporary hiccup during start-up could short-circuit things arbitrarily.
…d parent context for tracker state
…ontext() in web routes, and marks TODOs where needed
Quality Gate passedIssues Measures |
Wiring context through the EVM Keys API. Makes the db sql middleware added in #12097 more useful.